home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
telecomm
/
sticpsrc.lzh
/
HISTORY.ARC
/
HISTORY
Wrap
Text File
|
1990-08-25
|
48KB
|
1,119 lines
871225.33.PE1CHL.900813:
Fixed minor bugs in Turbo C version for the PC.
SCC driver now allows complete specification of the clocking mode, so that
all modems requiring- or providing external clocks can now be controlled.
The value to be written to WR11 of the Z8530 can now be specified as a
hexadecimal value after the existing baudrate specification, separated by a
colon (e.g. d1200:66). This is not necessary for the standard AFSK modems
and the HAPN 4800 baud modem, as these do not require external clocks.
Refer to a Z8530 technical manual for more information about the value to be
written to WR11.
871225.33.PE1CHL.900807:
Fixed a problem in the AX.25 forwarder: when no "r" or "w" line was present
in the script after "m" "u" or "b", the forwarder did not proceed.
Therefore it was impossible to forward to mailboxes that do not prompt for
the subject and/or the message, or don't send a CR after such prompts.
This is now fixed, and the following script works:
# forward test to personal mailbox
c 430 pe1chl-15
w>
# now we are connected, send each mail
l
mS%.0s %s
u%s
b
rOK
w>
n
This sends the S <call> command, the subject, and the entire message in one
go, and then checks for a response containing "OK". For more detail about
forwarding scripts see the explanation further down this file.
The forwarder now concatenates multiple lines from the message into a single
packet, whenever the total length of these lines is below paclen, except when
the effective window (maxframe) is less than 2.
The answer to a often-asked question about NET/ROM:
You can use different calls for the NET/ROM on different interfaces (e.g. a PI1
call on 23cm). Specify the calls you want to use in the "attach" commands for
the different interfaces. Somewhere after these attach commands the
autoexec.net file contains the line "attach netrom $CALLSIGN-9". When this
line is changed to "attach netrom" (without the callsign), the NET/ROM will use
the interface callsigns on each band. Make sure that you use a "hidden" alias
(starting with a # sign) for the interlink nodes of the NET/ROM! The alias can
be separately specified for each interface in the "netrom interface" lines.
871225.33.PE1CHL.900710:
On "exit", the program now waits for the interface queues to drain. This
should solve problems with param commands placed in "onexit.net". This often
did not function reliably because the interfaces were reset *before* the
characters were actually transmitted.
Atari version now supports up to 5 async channels. The 2 params after
"attach asy" (<addr> and <vec>) can now have the following values:
addr vec
1 0 ST RS232 port using Bcon* calls (BIOS)
1 1 ST RS232 port using direct access to fifo buffer
3 0 MIDI port
6 0 ST-compatible RS232 port on TT030
7 0 MODEM2 port on TT030
8 0 SERIAL1 port on TT030
9 0 SERIAL2 port on TT030
The old <addr> values 0 and 2 remain valid (for RS232 and MIDI).
Ports 6 and 7 could also be used on an ST with TOS 1.2 or higher, and a user-
written device driver (loaded from the AUTO folder) that supports the Bcon*
routines on BIOS devices 6 and 7. However, on an ST it is not possible to set
the mode and baudrate for these channels so your driver must set the port to
8bit, no parity, 1 stopbit, no handshake and the correct baudrate.
The driver must also supply a FIFO buffer for transmit and receive.
Unix/XENIX release. Only supports async I/O for now... (SLIP/KISS/NRS)
To attach a serial line, use an attach command like this:
attach asy /dev/tty1a 0 ax25 ax0 512 256 9600 pe1chl
- the tty device (/dev/tty1a) must be "disable"d, and have read/write permission
for the user running NET.
- the "0" value can be replaced by "r", "c" or "rc" to set the RTSFLOW and
CTSFLOW options for the device.
- the next two fields are the type (ax25) and name (ax0)
- the "512" is the size of the read() buffer used for receive
- the "256" is the MTU (paclen)
- the next fields are the speed (bits per second) and callsign
The program is available in 2 versions, net286 and net386. The '386 version
can use the select() function internally to improve efficiency. This can be
enabled by starting the program using: net386 select=kt
The 'k' and 't' enable the use of select() for keyboard(stdin) and tty devices.
It is also possible to set an environment variable SELECT to this value.
Testing using SCO XENIX386 release 2.3.2 has shown that the select() function
somehow clobbers the tty input and output buffers, so the use of this option is
not yet recommended.
The "dos" commands CD, COPY, TYPE, RENAME etc. are not implemented. Use a
subshell or a different window to perform these functions (except CD).
Incoming mail is stored in the /usr/spool/mail directory (or to the directory
defined by the NETMAILS). This directory must be writable by the user running
NET to be able to receive mail. The standard mailer can read the incoming mail,
but I do not yet know how to prepare outgoing mail. Mail stored in the
directory /usr/spool/mqueue (NETMAILQ), using the same format as in the DOS
version of NET, is transmitted by SMTP. This directory *must* exist and be
writable for the user running NET.
All configuration files are located in the "current directory" as effective when
the program is started. It is recommended to create a user "net", and to put
the configuration files and the program in it's home directory. NET can then
be started from the .profile, so that logging in as "net" is sufficient.
The FINGER files are stored in a subdirectory "finger", *without* the .txt
extension used by the DOS version of NET.
The TNC2 emulator will be implemented in a future release (using a FIFO).
871225.33.PE1CHL.900623:
Fixed problem that caused crash when an excluded station was connected from
the NET/ROM.
Many users complain about problems with IP and/or selected AX.25 servers.
Please note, that in this software each AX.25 server (defined using
"ax25 port") *must* have a *different* SSID, and that each interface (defined
using "attach") *must* have an SSID *different* from all SSID's used by AX.25
servers. Different interfaces may use the same SSID, but cross-band
digipeating will not be possible in that case.
The autoexec.net file provided as an example follows these rules, but many
people have modified the SSID's and subsequently had strange problems...
When you use the -0 SSID for an interface, the TNC server *must* have some
other SSID, or IP will not work. To avoid problems, everybody is hereby
encouraged to use the following SSID scheme (proposed by PE1LGT):
SSID Interf Function
-0 All TNC (normal ax.25 connect)
-1 All MBOX
-2 144 2m interface
-3 144 mheard/NetDigi 2m
-4 4k8 2m/4800 baud interface
-5 4k8 mheard/NetDigi 2m/4800 baud
-6 All Conference Bridge
-7 430 70cm interface
-8 430 mheard/NetDigi 70cm
-9 All NET/ROM
-10 aaaa interface
-11 aaaa mheard/NetDigi
-12 23cm 23cm interface
-13 23cm mheard/NetDigi 23cm
-14 bbbb interface
-15 bbbb mheard/NetDigi
aaaa en bbbb usable for other bands, e.g. 28 or 50 MHz
avoid using the -14 and -15 SSID's on bands where a local NET/ROM
is operating.
871225.33.PE1CHL.900611:
Atari version: moved disable/restore handler to trap #7, to allow the use
of trap #5 as a micro_rtx system call. This is only possible for MWC release
3.0.0 and above. No testing done with micro_rtx.
Fixed protocol problem that caused AX.25 failures when connected to G8BPQ
nodes.
Some changes made to improve portability. Attempt made to run under XENIX.
(it compiles okay, but the async port handling still causes headaches)